home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
InfoMagic Standards 1994 January
/
InfoMagic Standards - January 1994.iso
/
inet
/
ietf
/
pem
/
92mar.min
< prev
next >
Wrap
Text File
|
1993-02-17
|
2KB
|
38 lines
The Minutes below should be considered a Rough Draft - 3/26/92 Megan
Privacy Enhanced Mail Working Group
Report from meetings at the San Diego IETF
Steve Kent, Chair
The PEM WG met twice during the San Diego IETF meeting
3/16-20. The written comments provided John Linn (and distributed to
the PEM-DEV list) were reviewed and adopted. Several other changes
are being made to the specification based on additional written
comments from Jeff Schiller, plus PEM-DEV messages regarding encoding
of the signature as described at the end of Appendix A. One
significant change deals with the CRL database which was to be
maintained by the ICA. Now, each PCA will be responsible for
publishing a mail address to which CRL queries can be sent, and
another for CRL updates from CAs. It is the responsibility of the
PCAs, working with the ICA, to provide access to the complete CRL
database via these interfaces. details of the management of this
database will not be part of the RFC, as this is exclusively a PCA-ICA
interface issue. The description of the DN conflict detection
database has been revised and the specification of the protocol for
accessing this database will not appear as Appendix B, but rather will
become a separate document.
Generally the version of the document (1114E) distributed
prior to the meeting was well received and the consensus is that it is
almost ready for publication as an ID. A revised version of this
document (1114F) will be distributed immediately after the IETF
meeting, via the PEM-DEV mailing list. New versions of 1113 and 1115
should be available very soon, and an updated version of FORMS
(removing all the text not generally relevant to UAs) should be
forthcoming as well. The current plan calls for publication of all
four, updated documents as I-Ds as they become available, and then
submission of all four as standards track RFCs.